Release 2.9.0 #2400
Merged
Release 2.9.0 #2400
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Muralidhar Basani <[email protected]>
| @@ -219,4 +219,4 @@ Klaw (formerly Kafkawize) is maintained by, [Aiven](https://aiven.io/) open sour | |||
| Recent contributors are listed on the GitHub project page, | |||
| https://github.com/aiven/klaw/graphs/contributors | |||
|
|
|||
| Copyright (c) 2023 Aiven Oy and klaw project contributors. | |||
| Copyright (c) 2024 Aiven Oy and klaw project contributors. | |||
There was a problem hiding this comment.
good catch! We should check this on the docs as well
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Linked issue
Resolves: #xxxxx
Release 2.9.0 https://github.com/Aiven-Open/klaw/releases/edit/untagged-8ed6f64fce57227ead23
What kind of change does this PR introduce?
What is the current behavior?
Describe the state of the application before this PR. Illustrations appreciated (videos, gifs, screenshots).
What is the new behavior?
Describe the state of the application after this PR. Illustrations appreciated (videos, gifs, screenshots).
Other information
Additional changes, explanations of the approach taken, unresolved issues, necessary follow ups, etc.
Requirements (all must be checked before review)
mainbranch have been pulledpnpm linthas been run successfully